feat!: require Node.js 24 - #268
Merged
Merged
Conversation
Node.js 20 is past its end of life, and the tools of the repository need Node.js 22 at least. The packages declare Node.js 24 in `engines`, the repository is developed on Node.js 26 from `.tool-versions`, which every workflow reads now, and the unit tests run on Node.js 24 and on that version. BREAKING CHANGE: the packages require Node.js 24 or newer.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #268 +/- ##
==========================================
+ Coverage 85.74% 85.76% +0.02%
==========================================
Files 166 166
Lines 3766 3766
Branches 871 871
==========================================
+ Hits 3229 3230 +1
+ Misses 359 358 -1
Partials 178 178 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Node.js 20 reached its end of life on 2026-04-30, and the tools of the repository do not run on it anymore: vitest 5 needs
^22.12.0 || ^24.0.0 || >=26.0.0, size-limit 14^22.19.0 || ^24.5.0 || >=26.0.0, astro 7>=22.12.0. Theenginesof every package still said>=20, which nothing checked, since CI ran on Node.js 24 alone. The floor goes to 24 rather than 22 together with the 2.0.0 major, so the end of life of Node.js 22 on 2027-04-30 asks for no second breaking change.What
engines.nodeis>=24in the 20 published packages, the root andbenchmarks..tool-versionspins Node.js 26.10.0, the latest 26, which becomes an LTS on 2026-10-28. Everyactions/setup-nodestep reads it throughnode-version-file, so a bump of the file moves local development and CI together.unitjob runs on a matrix of Node.js 24, the floor the packages declare, and the version of.tool-versions, and uploads coverage from the latter alone.Notes
BREAKING CHANGEfooter.@types/nodestays^24, the floor, so the types catch an API of a newer Node.js.lint-package-jsonpasses, a frozen install gives no engine warnings and leaves the lockfile alone, the unit tests of kida, store and devtools pass, and size-limit of store measures the same bytes as on Node.js 24.